feat(analytics): remove additional filters from PaymentIntentFilters #6407
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
Hotfix PR for: #6403
Additional filters are added to
PaymentIntentFilters
as new analytics APIs are expected to be calculated fromSessionizer Payment Intents
table.Existing metrics on current dashboard are breaking due to these new filters as the fields are not present in the Payment Intents table.
Removed the following additional filters from
PaymentIntentFilters
Additional Changes
Motivation and Context
Closes: https://github.com/juspay/hyperswitch/issues/6404
Dashboard is raising error (status_code - 500) when payment intent based analytics APIs ae being hit, due to filter fields not present in the payment intents table.
How did you test it?
Added filters of connector, payment_method, etc on the dashboard and the payments v2 APIs should not return 500 error.
Checklist
cargo +nightly fmt --all
cargo clippy